Robot control system and method for introducing robot control software

ABSTRACT

An articulated robot is controlled by dynamically modifying a combination of a hardware dependent middleware layer and a hardware independent application layer. A memory device for storing a plurality of sets of robot hardware dependent software programs and a memory device for storing a plurality of sets of robot hardware independent software programs are prepared. During execution of software programs, a software program compatible with a robot hardware configuration is introduced from the former memory device, and this software program is dynamically combined with the set of hardware independent software programs. The robot is thus appropriately controlled, meeting the needs of users.

This is a continuation of copending International ApplicationPCT/JP01/08845 having an international filing date of Oct. 9, 2001.

TECHNICAL FIELD

The present invention relates to a robot control system which controlsan articulated robot such as a legged walking type robot using asoftware program, and relates a method of introducing a robot controlsoftware program. Particularly, the present invention relates to a robotcontrol system which controls, using a software program, an articulatedrobot which can substantially modify a hardware configuration when anoperation unit such as a head unit or a limb unit is mounted, demounted,or interchanged, and relates to a method of introducing a robot controlsoftware program. More particularly, the present invention relates to arobot control system which controls an articulated robot using asoftware program formed of a combination of a software layer largelydependent on a hardware configuration and a software layer independentof the hardware configuration, and relates to a method of introducing arobot control software program. The present invention also relates to arobot control system which controls an articulated robot by dynamicallymodifying a combination of a hardware dependent software layer such as amiddleware and a hardware independent software layer such as anapplication, and relates to a method of introducing a robot controlsoftware.

BACKGROUND ART

A machine that moves by means of electrical or magnetic effectsmimicking the behavior of a human is called a “robot.” The term robot issaid to be derived from Slavic word Robota (slave machine). In Japan,robots started to be widely used from the 1960s, and most of the robotswere then industrial robots such as manipulators and conveyance robotsfor automating a production line in a plant or for use in an unmannedplant.

Research and development have advanced in moving legged walking robotsthat use feet in walking and stable walk control for the moving robots,such as pet-type or toy robots which imitate the living mechanisms andthe behavior of quarupedalling animals such as the dog and the cat, and“human-like figured” or “human-type” robots (humanoid robots) whichimitate the living mechanism and the behavior of human beings or apes.Expectations of commercializing these robots are currently mounting. Thelegged walking robot is unstable and presents more difficulty in posturecontrol and walking control than crawling robots. However, the leggedwalking robot is excellent in that the legged walking robot is flexiblein walking and running, for instance, going up and down the stairs, andstriding over an obstacle.

An installed robot, such as a robot arm, which is firmly planted at aparticular location, is used for the assembling and selection of partsin a limited and local work space only. In contrast, the work space ofthe moving robot is not limited. The moving robot moves along apredetermined track or freely on a non-tracked area, performing any orpredetermined job conventionally manually done by humans. The movingrobot thus provides various services, instead of the human beings, thedogs, and other living things.

One of the applications of the legged walking robots is a diversity ofrisky and difficult jobs in industrial and production activities. Forinstance, in place of human beings, the legged walking robots areexpected to perform risky and difficult jobs such as maintenance work innuclear power plants, thermoelectric power plants, and petrochemicalplants, conveyance and assembly operation of parts in production plants,cleaning operations on high-rise buildings, and rescue activities in thesite of a fire.

Besides the above job assisting applications, the legged walking robotsmay perform a job which may be closely related to the livingenvironments of human beings, namely, “synergistic application” or“entertainment” applications. This type of robots emulates the behaviorof human beings or a variety of expressions of legged animals having arelatively high intelligence, such as dogs (pets), using the four legs.The robot not only performs faithfully an operation pattern inputbeforehand, but also dynamically responds to words and actions of a user(or another robot) (such as “praising”, “chastising”, or “beating”). Therobot is thus required to vividly respond to these actions and expresstheir emotions.

Conventional toy machines offer fixed interactive relationship with auser operation, and cannot be modified according to the user'spreference. As a result, the user may grow tired of the toy that simplyrepeats the same operation.

In contrast, intelligent robots have a behavior model and a learningmodel which responds to a stimulation, and thinks in a self-determiningmanner and performs operation control by determining a behavior bychanging the model in response to information input from outside, suchas a voice, an image, and tactile sensation. The robot, having anemotion model and an instinct model, behaves in a self-determiningmanner based on the emotion and the instinct of the robot itself. Withan image input device and a voice input and output device, the robotperforms an image recognition process and a voice recognition process.The robot thus communicates with humans in a realistic manner at ahighly intelligent level.

The legged walking robots currently have an excellent informationprocessing capability, and such intelligent robots may be regarded asone type of computation system.

The robots have a diversity of rules about action in the forms of anemotion model, a behavior model, and a learning model. The robot thendetermines a behavior plan in response to an external stimulation suchas a user action in accordance with these models, and carries out thebehavior plan through driving a joint actuator or voice output, therebygiving a feedback to the user. The operation control of the robot todetermine and carry out the behavior plan is performed by executing aprogram code (such as an application) on a computation system.

As for the main difference between an ordinary computation system and arobot, the computation systems are not so different in the type andcombination of hardware components (namely, a hardware configuration)forming the system from system to system. The robots are significantlydifferent in hardware configuration from robot to robot. For example,there is a diversity of legged walking robots. One robot includes atorso unit, and as movable units, a head unit, limb units, and a tailunit which are fixed to the torso unit. Another robot may be formed of ahead unit and wheels only.

In the computation systems which are relatively standardized in theinstalled hardware configuration from system to system, design ofsoftware program executed on the system is less subject to the systemhardware. In contrast, in the robot, the control software for operatingthe hardware is much more dependent on the hardware.

Now, moving control of a robot is considered. During movement andwalking, stability determination criteria are totally different betweenwhen movement means is moving feet and when the movement means is awheel, or between when the movement means is bipedaling and when themovement means is quadrupedaling, and thus, operation environments underwhich an application is performed are different from system to system.

In view of the above point, if the software layer less dependent onhardware is discriminated from the software layer more dependent onhardware, the software of the robot is efficiently developed.Specifically, hardware independent software and hardware dependentsoftware are individually developed, and a product lineup having adiversity of characteristics and performance levels is provided bycombining both types of software.

The hardware independent software includes applications that performprocesses such as those for the emotion model, the behavior model, andthe learning model, which are loosely related to hardware operation. Thehardware dependent software is a middleware composed of a group ofsoftware modules for providing a basic function of the robot. Theconstruction of each module is dependent on hardware attributes such aselectromechanical characteristics and specifications of the robot. Fromthe standpoint of function, middlewares may be mainly divided intorecognition middlewares which process and recognize a signal input toeach sensor and reports this signal to a hierarchically higherapplication, and output middlewares which control and drive hardware,such as each joint actuator, in response to a command issued by theapplication.

To permit any combination of applications and middlewares, a formataccording to which data and commands are exchanged between softwarelayers needs to be established, in other words, an interface betweenprograms needs to be established.

To introduce a software program into a variety of computation systemsincluding robots, a new software program may be fed in a removablemedium, or may be fed by downloading the software program through anetwork.

When a new software program is introduced into robots which aresubstantially different in hardware configuration from one to another,it is important that the introduced software be compatible with a targethardware configuration. Furthermore, it is necessary to assure that thenewly introduced software is compatible with other software layer (inother words, a compatibility between an application and a middlewareneeds to be assured).

DISCLOSURE OF THE INVENTION

It is an object of the present invention to provide an excellent robotcontrol system which controls an articulated robot, such as a leggedwalking type, using a software program, and to provide a method ofintroducing a robot control software program.

It is another object of the present invention to provide an excellentrobot control system which controls, using a software program, anarticulated robot which can substantially modify a hardwareconfiguration when an operation unit such as a head unit or a limb unitis mounted, demounted, or interchanged, and to provide a method ofintroducing a robot control software program.

It is yet another object of the present invention to provide anexcellent robot control system which controls an articulated robot usinga software program formed of a combination of a software layer largelydependent on a hardware configuration and a software layer independentof the hardware configuration, and to provide a method of introducing arobot control software program.

It is still another object of the present invention to provide a robotcontrol system which controls the articulated robot by dynamicallymodifying a combination of a hardware dependent software layer such as amiddleware and a hardware independent software layer such as anapplication, and to provide a method of introducing a robot controlsoftware.

The present invention has been developed in view of the above objects,and in one aspect relates to a robot control system which controls arobot including a combination of a plurality of hardware elements usinga hardware dependent software program and a hardware independentsoftware program. The robot control system includes hardware independentsoftware program providing means for providing the hardware independentsoftware program, hardware dependent software program providing meansfor providing at least one hardware dependent software program, hardwareconfiguration information acquisition means for acquiring hardwareconfiguration information of the robot, hardware dependent softwareprogram selection means for selecting a hardware dependent softwareprogram, compatible with the hardware configuration information acquiredby the hardware configuration information acquisition means, in thehardware dependent software providing means, and software introductionmeans for introducing, into the system, the hardware independentsoftware program provided by the hardware independent software programproviding means, and the hardware dependent software program selected bythe hardware dependent software selection means.

The term “system” here refers to a set of devices (or functional modulesfor carrying out a particular function) which is logically combined, andwhether the devices or the function modules are housed in a singlecasing is not important.

In accordance with the robot control system of the first aspect of thepresent invention, the hardware dependent software providing means,namely, a memory device for storing a plurality of sets of robothardware dependent software programs and the hardware independentsoftware providing means, namely, a memory device for storing aplurality of sets of robot hardware independent software programs areprepared. At the startup of the robot and during the execution ofsoftware programs, a software program compatible with a robot hardwareconfiguration is introduced from the former memory device, and thissoftware program is dynamically combined with the set of hardwareindependent software programs. The robot is thus appropriatelycontrolled, satisfying the needs of users.

The hardware independent software program and/or the hardware dependentsoftware program is provided by the memory device which is permanentlyfixed to the body of the robot and the memory device which isreplaceably mounted to the body of the robot.

A new software program and a software program satisfying the needs ofthe user may be fed to the body of the robot using the exchangeablememory device detachable from the robot body. The software introductionmeans controls the robot by using control software appropriatelysatisfying the needs of the user by introducing the hardware independentsoftware and/or the hardware dependent software from the exchangeablememory device with priority placed thereon.

The software introduction means introduces the hardware independentsoftware program and/or the hardware dependent software program from thefixed memory device when a usable hardware independent software programand/or a usable hardware dependent software program is not present inthe exchangeable memory device or when the exchangeable memory device isnot loaded.

The present invention in a second aspect relates to a robot controlsoftware program introducing method for introducing a hardware dependentsoftware program and a hardware independent software program into arobot including a combination of a plurality of hardware configurationelements, and includes a hardware independent software program providingstep for providing the hardware independent software program, a hardwaredependent software program providing step for providing at least onehardware dependent software program, a hardware configurationinformation acquisition step for acquiring hardware configurationinformation of the robot, a hardware dependent software programselection step for selecting a hardware dependent software program,compatible with the hardware configuration information acquired in thehardware configuration information acquisition step, and provided in thehardware dependent software providing step, and a software introductionstep for introducing, into a system, the hardware independent softwareprogram provided in the hardware independent software program providingstep, and the hardware dependent software program selected in thehardware dependent software selection step.

In accordance with the robot control system of the second aspect of thepresent invention, a memory device for storing a plurality of sets ofrobot hardware dependent software programs and a memory device forstoring a plurality of sets of robot hardware independent softwareprograms are prepared. At the startup of the robot and during theexecution of software programs, a software program compatible with therobot hardware configuration is introduced from the former memorydevice, and this software program is dynamically combined with the setof hardware independent software programs. The robot is thusappropriately controlled, thus satisfying the needs of users.

The hardware independent software program and/or the hardware dependentsoftware program is provided by the memory device which is permanentlyfixed to the body of the robot and the memory device which isreplaceably mounted to the body of the robot.

A new software program and a software program satisfying the needs ofthe user may be fed to the body of the robot using the exchangeablememory device detachable from the robot body. In the softwareintroduction step, operation control of the robot is performed by usingcontrol software appropriately satisfying the needs of the user byintroducing the hardware independent software and/or the hardwaredependent software from the exchangeable memory device with priorityplaced thereon.

In the software introduction step, the hardware independent softwareprogram and/or the hardware dependent software program is introducedfrom the fixed memory device when a usable hardware independent softwareprogram and/or a usable hardware dependent software program is notpresent in the exchangeable memory device or when the exchangeablememory device is not loaded.

The present invention in a third aspect relates to a robot controlsystem which controls a robot including a combination of a plurality ofhardware elements using a hardware dependent software program and ahardware independent software program, wherein the hardware independentsoftware program and/or the hardware dependent software program isprovided by a memory device which is permanently fixed to the body ofthe robot and a memory device which is replaceably mounted to the bodyof the robot, wherein the robot control system controls the robot in oneof a best match operation mode, an intercompatible operation mode, and afixed operation mode, and wherein in the best match operation mode, therobot is controlled using the hardware dependent software program andthe hardware independent software program introduced from theexchangeable memory, in the intercompatible operation mode, the robot iscontrolled using the hardware dependent software program introduced fromthe fixed memory device and the hardware independent software programintroduced from the exchangeable memory device, and in the fixedoperation mode, the robot is controlled using the hardware dependentsoftware program and the hardware independent software programintroduced from the fixed memory device.

A new software program and a software program satisfying the needs ofthe user may be fed to the body of the robot using the exchangeablememory device detachable from the robot body. The operation control ofthe robot is performed using control software appropriately satisfyingthe needs of the user by selecting the best match operation mode, theintercompatible operation mode, and the fixed operation mode in thatorder of priority.

Other objects, features, and advantages of the present invention becomeobvious from the following detailed description of the embodiments ofthe present invention, and the accompanying drawings.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 diagrammatically illustrates the hardware configuration of therobot in accordance with one embodiment of the present invention.

FIG. 2 illustrates a drive sub-unit 50, the configuration of which ismodified by mounting, demounting, and interchanging CPC components.

FIG. 3 is a diagram explaining the software configuration for robotcontrol.

FIG. 4 diagrammatically illustrates the software configuration providedby a fixed memory device 13.

FIG. 5 illustrates a modification of the software configuration providedby the fixed memory device illustrated in FIG. 4.

FIG. 6 diagrammatlically illustrates the software configuration providedby an exchangeable memory device 14.

FIG. 7 illustrates a modification of the software configuration providedby the exchangeable memory device 14 illustrated in FIG. 6.

FIG. 8 illustrates operation modes of a robot of this embodiment.

FIG. 9 is a flow diagram illustrating a process sequence for introducinga middleware and an application.

FIG. 10 illustrates a process for acquiring the hardware configurationof an actual robot and for comparing the hardware configuration withcompatible hardware configuration information.

FIG. 11 illustrates a system object which introduces a middleware and anapplication, namely, develops the middleware and the application in amain memory 12.

FIG. 12 illustrates the hardware of the robot formed of a plurality ofphysical components (CPC) which operates based on the applicationsupplied from outside through the exchangeable memory device 14.

FIG. 13 illustrates the robot formed of a variety of physical component(CPC) sets into which a middleware compatible with the hardwareconfiguration is introduced.

BEST MODE FOR CARRYING OUT THE INVENTION

The embodiments of the present invention are now discussed in detailreferring to the drawings.

FIG. 1 diagrammatically illustrates the hardware configuration of arobot in accordance with one embodiment of the present invention. Asshown, the hardware of the robot includes a control sub-system 10 and adrive sub-system 50.

The control sub-system 10 includes a CPU (Central Processing Unit) 11, amain memory 12, a fixed memory device 13, and an exchangeable memorydevice 14.

Under the control of a system control software, the CPU11 as a maincontroller executes a hardware independent software program such as anapplication and a hardware dependent software program such as amiddleware, thereby generally controlling the operation of the entirerobot.

The CPU11 is connected to memories and other circuit components, andperipheral devices through a bus. Each device over the bus is assigned aunique address (a memory address or an I/O address), and the CPU11communicates with a particular device by designating its address. Thebus is a general signal transmission line including an address bus, adata bus, and a control bus.

The main memory 12, typically a volatile memory formed of a plurality ofDRAMs (Dynamic Random Access Memory) chips, stores execution programcodes for the CPU11 and temporarily stores job data. In this embodiment,program codes such as the application and the middleware supplied fromthe fixed memory device 13 and the exchangeable memory device 14 aredeveloped, namely, mapped in a memory space in the main memory 12.

The fixed memory device 13 is a non-exchangeable non-volatile memoryfixed to the body of the robot. The fixed memory device 13 may be formedof a non-volatile memory element, which is programmed by applying awrite voltage, such as a flash memory.

The fixed memory device 13 is used to store program codes of anapplication for controlling the operation and thinking of the robot anda middleware for hardware operation. Since the fixed memory device 13 isfixed to the robot, the hardware dependent software such as themiddleware is preferably prepared with the version thereof set to becompatible with the hardware configuration at the shipment of the robot(default setting) or a standard hardware configuration.

The exchangeable memory device 14 is a non-volatile memory that isdetachably mounted to the robot. For example, the exchangeable memorydevice 14 is a cartridge memory medium such as a memory stick, and isloaded into a predetermined memory slot during use.

Like the fixed memory device 13, the exchangeable memory device 14 isused to store program codes such as an application for controlling theoperation and thinking of the robot, and a middleware for the operationof hardware. Since the exchangeable memory device 14, detachably mountedto the robot, is interchangeably used between different types ofhardware configurations, the exchangeable memory device 14 is used tosupply an up-to-date software program. There is not very high necessitythat the hardware dependent software such as the middleware is storedonto the exchangeable memory device 14 in a manner such that the versionthereof is set to be compatible with the hardware configuration at theshipment of the robot (default setting) or the standard hardwareconfiguration. It is preferred that the middleware providing theoperation environment to the hardware configuration for which theapplication is intended is combined with the application, and is thenstored onto the exchangeable memory device 14.

The drive sub-system 50 includes joint actuators, a drive circuit foreach actuator, an encoder for detecting the operation of each actuator,and a variety of sensors such as a camera and a touch sensor (all thesenot shown here). As shown, the drive sub-system 50 includes drive unitssuch as a head unit, a torso unit, and limb units.

At least some of the drive units are physical components (CPCs orConfigurable Physical Components) that can be dynamically reconfiguredby mounting, demounting, and interchanging units.

In this embodiment, each physical component is assigned uniqueidentification information, namely, a component ID. The CPU11 of thecontrol sub-system 10 (more specifically, the system control softwareexecuted by the CPU11) accesses each installed physical component via abus, thereby transferring a control command to each physical component,and acquiring each component ID. A combination of the detected IDcomponents becomes current hardware configuration information of therobot.

FIG. 2 illustrates the drive sub-unit 50, the configuration of which ismodified by mounting, demounting, and interchanging CPC components.Referring to FIG. 2(a), a plurality of physical components such as thetorso unit, and the head unit and the tail unit attached to the torsounit, is mounted. Referring to FIG. 2(b), a wheel is mounted to thetorso unit as a physical component.

As shown in FIGS. 2(aand 2(b), the same hardware dependent software isnot commonly used when the hardware configuration is substantiallychanged. For example, a middleware for receiving sensor inputs from thehead unit and the tail unit cannot operate on the apparatus having thehardware configuration shown in FIG. 2(b). Conversely, a middlewaredesigned to drive and control a limb unit as moving means cannot operateon the apparatus having the hardware configuration shown in FIG. 2(b).

The software configuration for controlling the robot is discussed belowreferring to FIG. 3. As shown, the robot control software includes anapplication layer, a middleware layer, and a system control layer. Thedesign of the software adopts object oriented programming. Theobject-oriented software is handled according to a module unit called an“object” into which data and the process procedure therefor areintegrated. Data communication is performed between the applicationlayer and the middleware layer through a predetermined programminginterface (also referred to as an “application interface”).

The application includes an emotion model which modelizes the emotion ofthe robot, an instinct model which modelizes the instinct of the robot,and a behavior model which modelizes a learning module for successivelystoring the cause and effect relationship between an external event andan action responsive thereto, and a behavior pattern. The applicationswitches an output destination for the action determined by the behaviormodel determined based on sensor input information, namely, an externalfactor.

The emotion model and the instinct model respectively receiverecognition result and behavior history, and manage an emotion value andan instinct value. The behavior model references these emotion value andinstinct value. The learning model updates behavior selectionprobability based on a learning guide provided from outside (by anoperator), and feeds the updated content to the behavior model.

The application performs a computation process using a model whichabstracts the configuration and behavior of the robot, and is a hardwareindependent software not influenced by hardware attributes.

The middleware layer is a set of software modules for providing a basicfunction of the robot. The construction of each module is a hardwaredependent software subject to the effect of the hardware attributes suchas electromechanical characteristics, the specifications and the shapeof the robot.

The middleware layer is functionally divided into a recognitionmiddleware and an output middleware.

The recognition middleware receives, from the hardware, raw data such asimage data, voice data, and other data detected by sensors, through thesystem control layer, and processes these pieces of data. Based on avariety of pieces of input information, the middleware performs voicerecognition, range detection, posture detection, touch sensing, motiondetection, and color recognition, thereby acquiring recognition results(for example, detecting a ball, detecting falling, detecting itselfbeing stroked, detecting being beaten, hearing one singing sol-fa,detecting a moving object, detecting an obstacle, recognizing anobstacle, etc.). The recognition results are reported to ahierarchically higher application through the application interface andare used to form a behavior plan.

The output middleware provides functions for walking, reproduction ofmovement, synthesis of output sound, and controls lighting of an LEDcorresponding to the eyes. Specifically, the output middleware receivesthe behavior plan formed in the application layer, generates a servocommand value for each joint of the robot per each function of therobot, the output sound, the output light (from the LED), and the outputvoice, and outputs these pieces of data, namely, performs on the robotthrough a virtual robot. In this arrangement, the application givesabstract action commands (for example, moving forward, moving backward,being pleased, barking, sleeping, performing bodily exercise, beingamazed, tracking), thereby controlling the joint actuators and otheroutput units on the robot body.

In this embodiment, the robot control software is fed to the apparatus 1by the fixed memory device 13 and the exchangeable memory device 14.

FIG. 4 diagrammatically illustrates the software configuration providedby a fixed memory device 13.

As shown, the fixed memory device 13 includes the application layer, themiddleware layer, and the system control layer. The software in eachlayer is developed on the main memory 12, namely, is mapped in thememory space of the main memory 12.

Since as already discussed, the fixed memory device 13 is permanentlyfixed to the apparatus, the hardware dependent software such as themiddleware is prepared with the version thereof set to be compatiblewith the hardware configuration at the shipment of the robot (defaultsetting) or the standard hardware configuration.

FIG. 5 illustrates a modification of the software configuration providedby the fixed memory device 13 illustrated in FIG. 4.

In the illustrated example, a plurality of middlewares compatible withdifferent hardware configurations is mounted. In order to immediatelydetermine whether the middleware in the fixed memory device 13 can drivethe robot apparatus 1, the fixed memory device 13 includes compatiblehardware configuration information which describes the hardwareconfiguration compatible with each middleware. The fixed memory device13 also includes a lookup table describing the correspondingrelationship between the hardware configuration and the middlewarecorresponding thereto.

The system control layer detects the hardware configuration of therobot, references the compatible hardware configuration information, andhardware-middleware lookup table, and then selectively introduces themiddleware compatible with the detected hardware configuration. Theintroduction process of the middleware will be described in detaillater.

FIG. 6 diagrammatically illustrates the software configuration providedby the exchangeable memory device 14.

As shown, the exchangeable memory device 14 includes an applicationlayer and a middleware layer. The software in each layer is developed,namely, mapped in the memory space of the main memory 12.

The exchangeable memory device 14 is detachably and replaceably mountedto the robot body, and is used interchangeably between apparatuseshaving different hardware configurations. The main usage of theexchangeable memory device 14 is to dynamically supply the robot with anupdated software version or an application the user wants to use, afterthe shipment of the robot. The middleware in the exchangeable memorydevice 14 is designed to be intended for the hardware configurationappropriate for the operation of the application.

Depending on the hardware configuration of a target robot in which theexchangeable memory device 14 is loaded, the hardware dependent softwaresuch as the middleware is not compatible with the hardware, in otherwords, cannot be introduced. Since the application layer is hardwareindependent in principle, it works on the middleware compatible with thehardware configuration of the robot (on the assumption that thecompatibility between the application and the middleware is assured).

FIG. 7 illustrates a modification of the software configuration providedby the exchangeable memory device 14 illustrated in FIG. 6.

In the illustrated example, a plurality of middlewares compatible withdifferent hardware configurations is mounted. In order to immediatelydetermine whether the middleware in the exchangeable memory device 14can drive the robot apparatus 1, the exchangeable memory device 14includes compatible hardware configuration information which describesthe hardware configuration compatible with each middleware. Theexchangeable memory device 14 also includes a lookup table describingthe corresponding relationship between the hardware configuration andthe middleware corresponding thereto.

The system control layer (already discussed) provided by the fixedmemory device 13 detects the hardware configuration of the robot,references the compatible hardware configuration information, andhardware-middleware lookup table, and then selectively introduces themiddleware compatible with the detected hardware configuration.

As understood from FIG. 4 through FIG. 7, the application is suppliedfrom each of the fixed memory device 13 and the exchangeable memorydevice 14. The application is independent of the hardware configuration.In principle, the application normally operates on the robot through themiddleware compatible with the hardware configuration, regardless ofwhether it is in the fixed memory device 13 or the exchangeable memorydevice 14.

In this embodiment, the application and the middleware supplied by theexchangeable memory device 14 are installed with priority. The reason isas follows. An up-to-date software version or a software version theuser prefers is selected by transferring the software by means of theexchangeable memory device 14. The design of the middleware on theexchangeable memory device 14 is intended for the hardware configurationof the robot appropriate for the operation of the application.

The system control layer (previously described) provided by the fixedmemory device 13 introduces the application and the middleware.Specifically, the system control layer detects the hardwareconfiguration of the robot, references the compatible hardwareconfiguration information and the hardware-middleware lookup table, andthen selectively introduces the middleware compatible with the detectedhardware configuration. The introduction process procedure of themiddleware will be discussed in detail later.

FIG. 8 illustrates operation modes of the robot of this embodiment. Asshown, the robot works in three operation modes, i.e., a “best matchoperation mode”, an “intercompatible operation mode”, and a“fixed-operation mode”.

In the best match operation mode, both the application and themiddleware introduced from the exchangeable memory device 14 are used.

In this operation mode, the application dynamically supplied to therobot after the shipment of the robot is used in response to a requestfrom the user. The middleware that is designed in accordance with theoperation of the application may be introduced from the exchangeablememory device 14 for use.

In the intercompatible operation mode, the application introduced fromthe exchangeable memory device 14 is operated on the middlewareintroduced from the fixed memory device 13.

In this operation mode, the application dynamically supplied to therobot after the shipment of the robot is used in response to the requestfrom the user.

This operation mode is accomplished by furnishing a predeterminedprogramming interface, namely, compatibility between the application ofthe exchangeable memory device 14 and the middleware of the fixed memorydevice 13.

In the fixed operation mode, both the application and the middleware areintroduced from the fixed memory device 13.

Since an up-to-date software version or a software version satisfyingthe needs of the user is transferred between the apparatuses, thesoftware introduction is performed from the exchangeable memory device14 with priority placed thereon. In other words, the robot performs thebest match operation mode, the intercompatible operation mode, and thefixed operation in that priority order. The fixed operation mode isperformed when the exchangeable memory device 14 is not loaded into therobot.

The process of introducing the software into the robot is discussedbelow.

FIG. 9 is a flow diagram illustrating the process sequence forintroducing the middleware and the application. The system control layer(previously discussed) provided by the fixed memory device 13 performsthe introduction process procedure during a boot process of the robotbody. The introduction process of the software is discussed below inaccordance with the flow diagram.

The system control layer accesses each physical component (CPC) ofhardware via the bus, reads the component ID of each component, andacquires the hardware configuration (step S1).

The system control layer attempts to access the exchangeable memorydevice 14 (step S2).

When the exchangeable memory device 14 is not installed, the middlewareand the application are introduced from the fixed memory device 13, aredeveloped on the main memory 12 (steps S10, and S11), and the fixedoperation mode is activated.

When the middleware is introduced from the fixed memory device 13 instep S10, the system control layer references the hardware configurationinformation and the hardware-middleware lookup table in the fixed memorydevice 13, and selectively introduces the middleware compatible with thehardware configuration detected in step S1, in other words, develops themiddleware on the main memory 12.

On the other hand, when exchangeable memory device 14 is installed onthe robot body, the system control layer reads the compatible hardwareconfiguration information within the exchangeable memory device 14,compares the compatible hardware configuration information with thehardware configuration of the robot body detected in step S1, and checkscompatibility with the middleware (steps S4, and S5).

When no hardware configuration information coinciding with the hardwareconfiguration of the robot body is found in the exchangeable memorydevice 14, there is no middleware in the exchangeable memory device 14operable on the robot body. In such a case, the middleware from thefixed memory device 13 is introduced, namely, developed on the mainmemory 12 (step S8). Also, the application from the exchangeable memorydevice 14 is introduced, namely, developed on the main memory 12 (stepS9), and the intercompatible operation mode is thus activated.

When the middleware is introduced from the fixed memory device 13 instep S8, the system control layer may reference the compatible hardwareconfiguration information and the hardware-middleware lookup table inthe fixed memory device 13, and may selectively introduce the middlewarecompatible with the hardware configuration detected in step S1.

When the hardware configuration information coinciding with the hardwareconfiguration of the actual robot body is found in the exchangeablememory device 14, the system control layer references thehardware-middleware lookup table to check whether a middlewarecompatible with the hardware configuration of the robot body is present.The middleware is introduced, namely, developed on the main memory 12(step S6). In succession, the system control layer introduces theapplication from the exchangeable memory device 14, namely, develops theapplication on the main memory 12 (step S7), and the best matchoperation mode is activated.

FIG. 10 illustrates a process for acquiring the hardware configurationof the actual robot and for comparing the hardware configuration withcompatible hardware configuration information. The comparison process ofthe hardware configuration information is carried out by the systemcontrol layer. The system control layer installed through theobject-oriented programming is hereinafter referred to as a “systemobject.”

In the illustrated example, the actual robot body includes physicalcomponents (CPC), such as a torso unit, limb units, a head unit, and atail unit. The system object accesses, in hardware, the physicalcomponents through the bus, and acquires each component ID. In thiscase, the hardware configuration of the robot is {torso ID, limb ID,tail ID, and head ID}.

The fixed memory device 13 and the exchangeable memory device 14respectively have compatible hardware configuration information filescalled design A and design B. Here, the design A includes the compatiblehardware configuration {torso ID, limb ID, tail ID, and head ID}, andthe design B includes the compatible hardware configuration {torso IDand four wheel ID}.

The system object compares the hardware configuration informationacquired from the actual robot body with each compatible hardwareconfiguration information, and selects the compatible hardwareconfiguration information file compatible with the actual robotapparatus. As shown in the illustrated example, the compatible hardwareconfiguration information file related to the design A is selected.

The system object references the hardware-middleware lookup table in thefixed memory device 13 or the exchangeable memory device 14, searchesfor the middleware which is determined to be compatible with the robotin hardware configuration, and introduces the middleware and theapplication.

FIG. 11 illustrates the system object which introduces the middlewareand the application, namely, develops the middleware and the applicationin the main memory 12.

In this embodiment, the application and the middleware are designedthrough object-oriented programming.

An application file composed of an object X, an object Y, and an objectZ is stored in the exchangeable memory device 14. Each objectcommunicates with the system object through a virtual object.

A middleware file composed of an object A, an object B, and an object Cis stored in the fixed memory device 13. Each object communicates withthe system object through a virtual object. The middleware is compatiblewith the hardware configuration information of the above-mentioneddesign A.

A middleware file composed of an object D and an object E is stored inthe exchangeable memory device 14. Each object communicates with thesystem object through a virtual object. The middleware is compatiblewith the hardware configuration of the above-mentioned design B.

Now, the system object determines that the hardware configurationinformation of the actual robot is the design A. In such a case, thesystem object searches the hardware-middleware lookup table in each ofthe exchangeable memory device 14 and the fixed memory device 13 for themiddleware file compatible with the design A within the fixed memorydevice 13. Through the virtual object, the object A, the object B, andthe object C forming the middleware file are introduced, namely,developed on the main memory 12.

The system object communicates with the object forming the applicationfile in the exchangeable memory device 14 through the virtual object,thereby introducing the object X, the object Y, and the object Z formingthe application, namely, developing these objects on the main memory 12.

The introduction of the middleware is performed by substituting anactual object for a portion of the virtual object in the middleware filein the fixed memory device 13, and by loading the resulting file on themain memory 12. The memory loading operation is carried out by thesystem object.

The interchanging; process of the application for driving the robot isdiscussed below.

As described above, besides the application, the middleware for whichthe application is intended is stored in the exchangeable memory device14 such as the memory stick. When the robot apparatus is equipped withthe hardware configuration on which the middleware, for which theapplication is intended, is operable, the middleware is introduced fromthe exchangeable memory device 14, rather than the middleware in thefixed memory device 13. Otherwise, the application introduced from theexchangeable memory device 14 is operated on the middleware introducedfrom the fixed memory device 13.

FIG. 12 illustrates the hardware of the robot formed of a plurality ofphysical components (CPC) which operates based on the applicationsupplied from outside through the exchangeable memory device 14.

The robot body includes, for example, physical component (CPC) sets foraccomplishing a quadrupedaling action, and four-legged middleware(tentative term) for providing an operation environment for afour-legged CPC set. In this example, the four-legged middleware isintroduced from the fixed memory device 13, and is referred to as a“root CPC” middleware closely related to the hardware configuration ofthe actual robot.

At a play 1 phase, an application A, introduced from the exchangeablememory device 14, drives and controls the four-legged CPC on the rootCPC middleware.

At a play 2 phase, an application B, introduced from the exchangeablememory device 14, drives and controls the four-legged CPC set on theroot CPC middleware.

At the play 2 phase, the application A, again introduced from theexchangeable memory device 14, drives and controls the four-legged CPCon the root CPC middleware.

The interchanging process of the middleware providing the operationenvironment of the robot will now be discussed.

At least one of the physical components forming the robot body isdetachably and interchangeably mounted, and the CPC set is modified byinterchanging the physical component. For example, the four legs as themoving means may be replaced with the four wheels to configure the robothaving a four-wheeled CPC set.

As the hardware configuration is dynamically modified in this way, themiddleware providing an operation environment needs to be changed fromthe CPC (the four-legged CPC) middleware to a middleware forfour-wheeled CPC set driving. In such a case, like an applicationprogram, the new middleware is fed from outside through the exchangeablememory device 14, and then introduced into the main memory 12.

The exchangeable memory device 14 stores, besides the application, themiddleware compatible with the hardware configuration for which theapplication is intended for. When the robot equipped with theexchangeable memory device 14 contains that hardware configuration, themiddleware is introduced from the exchangeable memory device 14 and theoperation environment is thus provided. Otherwise, the applicationintroduced from the exchangeable memory device 14 is executed under thenative operation environment provided by the middleware of the fixedmemory device 14.

FIG. 13 illustrates the robot formed of a variety of physical component(CPC) sets into which the middleware compatible with the hardwareconfiguration is introduced.

Referring to FIG. 13(a), the robot contains the four-legged CPC setwhich is a default setting at the shipment thereof. In such a case, therobot is furnished with the operation environment provided by the rootCPC middleware introduced from the fixed memory device 13. A variety ofapplications (the application A in the illustrated example) introducedthrough the exchangeable memory device 14, which is interchanged by theuser, is executed on the root CPC middleware.

Referring to FIG. 13(b), the hardware configuration is modified from thefour-legged CPC set to the four-wheeled CPC set through a robot CPCinterchanging operation. In such a case, the four-legged root CPCmiddleware cannot not be used as is. The middleware intended forfour-wheeled CPC set driving, namely, the four-wheeled root CPCmiddleware, is introduced from outside through the exchangeable memorydevice 14. A variety of applications (the application B in theillustrated example) introduced through the exchangeable memory device14 is executed under the operation environment provided by thefour-wheeled root CPC middleware.

Referring to FIG. 13(c), the hardware configuration of the robot remainsunchanged from the four-wheeled CPC set, but the operation environmentis modified to a new middleware having a new function of four-wheeledCPC set driving, namely, a new root CPC set for four-wheel driving. Themiddleware intended for the driving of the new four-wheeled CPC set,namely, the new four-wheeled root CPC middleware is introduced fromoutside through the exchangeable memory device 14. A variety ofapplications (the application B in the illustrated example) introducedthrough the exchangeable memory device 14 is executed under theoperation environment provided by the new four-wheeled root CPCmiddleware.

It should be noted that the same application is executed on robots of avariety of hardware configurations by successively introducingmiddlewares compatible with the hardware configuration of the actualrobot.

This embodiment is based on the assumption that a software layerrelatively less dependent on hardware, namely, an application, and asoftware layer relatively more dependent on hardware, namely, amiddleware layer, are independently handled. With the independence ofapplication and client assured, the following functions are performed.

(1) A single application may be compatible with a robot having a varietyof hardware configurations. (The user may transfer an application owned(or grown) by the user himself or herself from robot to robot, or maycirculate the application for sale.

(2) A middleware compatible with a variety of applications is producedon a robot having a single hardware configuration. Since the middlewarehas a high reusability, development efficiency of the applicationincreases.

(3) Even with the same application on the robot having the same hardwareconfiguration, actual expressive power and controllability are enhancedby modifying the middleware.

(4) Since binary compatibility is assured, binary codes such as anapplication or a middleware is downloaded to the robot from theexchangeable memory device 14. The software is thus simply interchangedwith the above advantages enjoyed. Without a compile job, softwareinterchanging is performed.

(5) Since the application is independent of the middleware, softwaredevelopment vendors can focus on function development in their specialtyfield. For example, a vendor developing control systems concentrates onthe development of middleware, and uses a variety of applications.

Appendix

The present invention has been detailed referring to particularembodiments. It is however obvious that ordinary skilled artisans easilymodify and change the embodiments without departing from the scope ofthe present invention.

The subject of the present invention is not necessarily limited toproducts called “robots”. The present invention is equally applicable toany machines, which move mimicking the behavior of humans by means ofelectrical and magnetic effects. For example, the present invention isapplicable to products in other industrial fields, such as toys.

The present invention has been disclosed with reference to exemplaryembodiments, and should not be understood as limiting the scope of thepresent invention. In the determination of the scope of the presentinvention, the preceding claims should be referred to.

INDUSTRIAL APPLICABILITY

The present invention provides an excellent robot control system whichcontrols an articulated robot such as legged walking type using asoftware program, and provides a method of introducing a robot controlsoftware program.

The present invention provides an excellent robot control system whichcontrols, using a software program, an articulated robot which cansubstantially modify a hardware configuration when an operation unitsuch as a head unit or a limb unit is mounted, demounted, orinterchanged, and provides a method of introducing a robot controlsoftware program.

The present invention provides an excellent robot control system whichcontrols an articulated robot using a software program formed of acombination of a software layer largely dependent on a hardwareconfiguration and a software layer independent of the hardwareconfiguration, and provides a method of introducing a robot controlsoftware program.

The present invention provides a robot control system which controls thearticulated robot by dynamically modifying a combination of a hardwaredependent software layer such as a middleware and a hardware independentsoftware layer such as an application, and provides a method ofintroducing a robot control software.

The present invention, including a memory device for storing a pluralityof sets of robot hardware dependent software programs and,a memorydevice for storing a plurality of sets of robot hardware independentsoftware programs, introduces a software program compatible with a robothardware configuration from the former memory device at the startup ofthe robot or during the execution of the software program, anddynamically combining the software program with the software setindependent of the hardware configuration. The robot is thusappropriately controlled, thereby satisfying the needs of users.

What is claimed is:
 1. A robot control system which controls a robot including a combination of a plurality of hardware elements using a hardware dependent software program and a hardware independent software program, the robot control system comprising: hardware independent software program providing means for providing the hardware independent software program, hardware dependent software program providing means for providing at least one hardware dependent software program, hardware configuration information acquisition means for acquiring hardware configuration information of the robot, hardware dependent software program selection means for selecting a hardware dependent software program, compatible with the hardware configuration information acquired by the hardware configuration information acquisition means, in the hardware dependent software providing means, and software introduction means for introducing, into the system, the hardware independent software program provided by the hardware independent software program providing means, and the hardware dependent software program selected by the hardware dependent software selection means.
 2. A robot control system according to claim 1, further comprising a memory device which is permanently fixed to the body of the robot, wherein the hardware independent software program and/or the hardware dependent software program is provided by the fixed memory device.
 3. A robot control system according to claim 1, further comprising a memory device which is replaceably mounted to the body of the robot, wherein the hardware independent software program and/or the hardware dependent software program is provided by the exchangeable memory device.
 4. A robot control system according to claim 1, further comprising a memory device which is permanently fixed to the body of the robot, and a memory device which is replaceably mounted to the body of the robot, wherein the hardware independent software program and/or the hardware dependent software program is provided by the fixed memory device and the exchangeable memory device, and wherein the software introduction means introduces the hardware independent software program and/or the hardware dependent software program from the exchangeable memory device with priority placed thereon.
 5. A robot control system according to claim 4, wherein the software introduction means introduces the hardware independent software program and/or the hardware dependent software program from the fixed memory device when a usable hardware independent software program and/or a usable hardware dependent software program is not present in the exchangeable memory device or when the exchangeable memory device is not loaded.
 6. A robot control software program introducing method for introducing a hardware dependent software program and a hardware independent software program into a robot including a combination of a plurality of hardware configuration elements, the method comprising: a hardware independent software program providing step for providing the hardware independent software program, a hardware dependent software program providing step for providing at least one hardware dependent software program, a hardware configuration information acquisition step for acquiring hardware configuration information of the robot, a hardware dependent software program selection step for selecting a hardware dependent software program, compatible with the hardware configuration information acquired in the hardware configuration information acquisition step, and provided in the hardware dependent software providing step, and a software introduction step for introducing, into a system, the hardware independent software program provided in the hardware independent software program providing step, and the hardware dependent software program selected in the hardware dependent software selection step.
 7. A robot control software program introducing method according to claim 6, wherein the robot comprises a memory device which is permanently fixed to the body of the robot, and wherein the hardware independent software program and/or the hardware dependent software program is provided by the fixed memory device.
 8. A robot control software program introducing method according to claim 6, wherein the robot comprises a memory device which is replaceably mounted to the body of the robot, and wherein the hardware independent software program and/or the hardware dependent software program is provided by the exchangeable memory device.
 9. A robot control software program introducing method according to claim 8, wherein the robot comprises a memory device which is permanently fixed to the body of the robot, and a memory device which is replaceably mounted to the body of the robot, wherein the hardware independent software program and/or the hardware dependent software program is provided by the fixed memory device and the exchangeable memory device, and wherein the software introducing step introduces the hardware independent software program and/or the hardware dependent software program from the exchangeable memory device with priority placed thereon.
 10. A robot control software program introducing method according to claim 9, wherein the software introduction means introduces the hardware independent software program and/or the hardware dependent software program from the exchangeable memory device when a usable hardware independent software program and/or a usable hardware dependent software program is not present in the exchangeable memory device or when the exchangeable memory device is not loaded.
 11. A robot control system which controls a robot including a combination of a plurality of hardware elements using a hardware dependent software program and a hardware independent software program, wherein the hardware independent software program and/or the hardware dependent software program is provided by a memory device which is permanently fixed to the body of the robot and a memory device which is replaceably mounted to the body of the robot, wherein the robot control system controls the robot in one of a best match operation mode, an intercompatible operation mode, and a fixed operation mode, and wherein in the best match operation mode, the robot is controlled using the hardware dependent software program and the hardware independent software program introduced from the exchangeable memory device, in the intercompatible operation mode, the robot is controlled using the hardware dependent software program introduced from the fixed memory device and the hardware independent software program introduced from the exchangeable memory device, and in the fixed operation mode, the robot is controlled using the hardware dependent software program and the hardware independent software program introduced from the fixed memory device.
 12. A robot control system according to claim 11, wherein one of the best match operation mode, the intercompatible operation mode, and the fixed operation mode is selected. 